- 3 minutes to read

Monitoring Azure Event Hub Logger

Learn how to monitor the Azure API Management Service Event Hub Logger

Nodinite also has Monitoring for these other Azure API Management Service types:

This page provides documentation about Azure API Management Service Event Hub Logger Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the state of Azure API Management Service Event Hub Loggers, as specified by system-defined thresholds, either global or specific. You can manage configured Azure API Management Services Event Hub Loggers; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Azure API Management Service Certificates page.

Azure API Management Service Certificates as Resources
Example list of monitored Azure API Management Services Event Hub Loggers in a Nodinite Monitor View

Monitoring Features

  • State Evaluation - Provide state according to user-defined thresholds.

    If Nodinite can't check your Azure API Management Service items' state, chances are no one else can use them either.

  • Services have Automatic Discovery
    • The Nodinite Azure Agent makes use of the Azure Rest API. Hence, the Azure API Management Services Event Hub Loggers are dynamically managed.
  • Category-based monitoring - The Azure API Management Service Event Hub Logger belongs to the Category API Management Service - Certificate
  • Share access to individual Event Hub Loggers from within Nodinite using one or more role-based Monitor Views.
  • The Application name is constructed as /ConfigurationName/ResourceGroupName/API Management Service Name/. This naming scheme provides uniqueness, even if you deploy the same set of artifacts/services with the same name in different Monitored Azure Subscriptions.
    ApplicationPathExample

State evaluation for Azure API Management Service Certificates

The configured Subscriptions with Azure API Management Services Event Hub Loggers to monitor manifests within Nodinite as one or more Resources. For example, if you have two Services, you will have two Resources in Nodinite.

  • The Nodinite Resources name is the name of the deployed Certificate.

Each item (presented in Nodinite as a Resource) evaluates with a state (i.e. OK, Warning, Error, Unavailable).

You can override the evaluation process by configuring the Expected State option available for all Nodinite Resources.

API Management Service Certificate

For API Management Service - Certificate, the state evaluates as described in the table below:

State Status Description Actions
Unavailable Resource not available
  • Evaluation of the 'API Certificate' is not possible either due to network or security-related problems
Review prerequisites
Error Error threshold is breached Certificate is about to expire or has already expired
Warning Warning threshold is breached Certificate is about to expire or has already expired
OK Within user-defined thresholds Operational Edit thresholds
Details

Alert history for Azure API Management Service

During root cause analysis or other purposes, it might be useful to understand how often your Azure API Management Service problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span either for all your Azure API Management Service or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.

Search Resource history

Search for alert history for all resources in the Monitor View

Alert history for the selected Azure API Management Service item

Frequently asked questions

Use the troubleshooting guide to find the FAQ and answers to known problems.


Next step